Assessing completion of events

ABSTRACT

A method for assessing completion of events in a network environment is provided. The method includes receiving a first event vector, generating a second event vector, machine matching the first event vector to the second event vector, and generating an output that includes a variable indicating whether an event corresponding to the first event vector is complete. If each of a plurality of first nodes of the first event vector matches a corresponding one of a plurality of the second nodes of the second event vector, the variable indicates that the event corresponding to the first event vector is complete. If at least one of the plurality of the first nodes of the first event vector is mismatched with the corresponding one of the plurality of the second nodes of the second event vector, the variable indicates that the event corresponding to the first event vector is incomplete.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119 to U.S.Provisional Application No. 62/576,931, filed Oct. 25, 2017, U.S.Provisional Application No. 62/589,069, filed Nov. 21, 2017, and U.S.Provisional Application No. 62/581,343, filed Nov. 3, 2017. All of theseapplications are hereby incorporated by reference in their entiretiesfor all purposes.

BACKGROUND

This specification relates in general to assessing completion of eventsin a network environment. For example, completion of events maycorrespond to compliance with protocols. However, manual tracking ofcompliance with protocols may be slow and burdensome.

BRIEF DESCRIPTION OF THE DRAWINGS

Various examples in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 is an example block diagram illustrating an interaction system inwhich techniques relating to assessing completion of events may beimplemented, according to at least one example;

FIG. 2 is an example block diagram illustrating an interaction system inwhich techniques relating to assessing completion of events may beimplemented, according to at least one example;

FIG. 3 is an example schematic model illustrating a networkcommunication model in which techniques relating to assessing completionof events may be implemented, according to at least one example;

FIG. 4 is an example schematic model illustrating an aspect of thenetwork communication model of FIG. 3 in more detail;

FIG. 5 is an example schematic model illustrating an aspect of thenetwork communication model of FIG. 3 in more detail;

FIG. 6 is an example schematic model illustrating an aspect of thenetwork communication model of FIG. 3 in more detail;

FIG. 7 is an example schematic model illustrating an aspect of thenetwork communication model of FIG. 3 in more detail;

FIG. 8 is an example schematic architecture illustrating an interactionsystem in which techniques relating to assessing completion of eventsmay be implemented, according to at least one example;

FIG. 9 is an example schematic model illustrating a system for analyzingcompliance with a protocol, according to at least one example;

FIG. 10 illustrates event vectors for assessing completion of events,according to at least one example;

FIGS. 11A-11C are example diagrams of a facility in which techniquesrelating to assessing completion of events may be implemented, accordingto at least one example;

FIG. 12 is an example schematic architecture illustrating a system inwhich techniques relating to assessing completion of events may beimplemented, according to at least one example;

FIG. 13 is an example diagram illustrating an aspect of the system ofFIG. 12 in more detail;

FIG. 14 is an example diagram of protocols that may be implemented,according to at least one example;

FIGS. 15A-15D are example schematic models of presence time processors,according to at least one example;

FIG. 16 is an example flowchart for determining whether a protocol wasperformed, according to at least one example;

FIG. 17 is an example flowchart for resolving an event, according to atleast one example;

FIG. 18 is an example flowchart for generating documentation, accordingto at least one example; and

FIG. 19 is an example flowchart for modifying recorded presence time,according to at least one example.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) only,and is not intended to limit the scope, applicability or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiment(s) will provide those skilled in the art with anenabling description for implementing a preferred exemplary embodiment.It is understood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

Referring first to FIG. 1, a block diagram of an example of aninteraction system 100 is illustrated. Generally, in interaction system100, data can be generated at one or more system components 102 and/oruser devices 104. Management engine 106 can manage the flow ofcommunications within interaction system. Transformative processingengine 108 can receive, intercept, track, integrate, process, and/orstore such data.

Data flowing in interaction system 100 can include a set ofcommunications. Each of one, some of all communications can include (forexample) an encoding type, authentication credential, indication of acontent size, identifier of a source device, identifier of a destinationdevice, identifier pertaining to content in the communication (e.g., anidentifier of an entity), a processing or reporting instruction, aprocedure specification, transmission time stamp, and/or sensormeasurement. Data may, or may not, selectively pertain to a particularentity and/or client. Data can, depending on the implementation, includeindividually identifiable information and/or de-identified informationas it pertains to an entity and/or client. Data may, but need not,include protected information.

For example, a system component 102 can include, for example, a sensorto detect a sensor measurement and can thereafter generate and transmita communication that reflects the sensor measurement. The communicationmay be transmitted at routine times and/or upon detecting a threshold(e.g., one or more) number of measurements or a measurement satisfying atransmission condition (e.g., exceeding a threshold value). In someinstances, the sensor measurement corresponds to one reflecting aproperty of an object or entity (e.g., person) near the sensor. Thecommunication may then include an identifier of the object or entity.The identifier can be determined, for example, based on detection of anearby electronic tag (e.g., RFID tag), a detected user input receivedat a user interface of component 102, and/or data in a correspondingcommunication received from a user device.

As another example, a user device 104 can be configured to detect inputreceived at an interface of the device. The input can include, forexample, an identifier of an object or entity, an instruction, acharacterization of an object or entity, an identification of anassessment to be performed, a specification of an aggregation or dataprocessing to be performed, and/or an identification of a destinationfor a data-analysis report. User device 104 can further be configured todetect input requesting particular data, to generate a requestcommunication (e.g., to be sent to transformative processing engine), toreceive the requested data and/or to present the received data.

The depicted engines, devices and/or components can communicate over oneor more networks. A network of one or more networks can include a wirednetwork (e.g., fiber, Ethernet, powerline ethernet, ethernet overcoaxial cable, digital signal line (DSL), or the like), wireless network(e.g., Zigbee™, Bluetooth™, WiFi™, IR, UWB, WiFi-Direct, BLE, cellular,Long-Term Evolution (LTE), WiMax™, or the like), local area network, theInternet and/or a combination thereof. It will be appreciated that,while one or more components 102 and one or more user devices 104 areillustrated as communicating via transformative processing engine 108and/or management engine 106, this specification is not so limited. Forexample, each of one or more components 102 may communicate with each ofone or more user devices 104 directly via other or the samecommunication networks.

A component 102 can be configured to detect, process and/or receivedata, such as environmental data, geophysical data, biometric data,chemical data (e.g., chemical composition or concentration analysisdata), and/or network data. The data can be based on data detected, forexample, via a sensor, received signal or user input. A user device 104can include a device configured to receive data from a user and/orpresent data to a user. It will be appreciated that, in some instances,a component 102 is also a user device 104 and vice-versa. For example, asingle device can be configured to detect sensor measurements, receiveuser input and present output.

A component 102 can be configured to generate a communication that is inone or more formats, some of which can be proprietary. For example, animaging machine (e.g., one of one or more components 102) manufacturedby company A, located within a first facility (e.g., facility 110), andbelonging to a first client, may save and transfer data in a firstformat. An imaging machine (e.g., one of one or more components 102)manufactured by company B, located within the first facility (e.g.,facility 110), and belonging to the first client, may save and transferdata in a second format. In some examples, data from certain componentsis transformed, translated, or otherwise adjusted to be recognizable bytransformative processing engine 108. Thus, continuing with the examplefrom above, when the imaging machines manufactured by companies A and Bare located within the first facility belonging to the first client,they may nevertheless save and transfer data in different formats. Insome examples, one or more components 102 communicate using a definedformat.

In some examples, each of one or more components 102 are each associatedwith one or more clients within a same or different interaction systems.For example, certain ones of one or more components 102 may beassociated with a first client, while other ones of one or morecomponents 102 may be associated with a second client. Additionally,each of one or more components 102 may be associated with a facility 110(e.g., client facility). Each facility 110 may correspond to a singlelocation and/or focus. Exemplary types of facilities include server farmfacilities, web-server facilities, data-storage facilities,telecommunication facilities, service facilities, and/or operationalfacilities. For example, a first facility may include a structure at afirst location at which one or more resources (e.g., computationalresources, equipment resources, laboratory resources, and/or humanresources) are provided. Each of the one or more resources may be of afirst type in a first set of types. A resource type can be identifiedbased on, for example, a characteristic of the resource (e.g., sensorinclusion) and/or a capability of providing each of one or moreservices. Thus, for example, resources at a first facility may be betterconfigured for handling a particular type of service requests comparedto those in another facility. As another example, different facilitiesmay include resources of similar or same types but may vary in terms of,for example, accessibility, location, etc.

Transmission of data from one or more components 102 to transformativeprocessing engine 108 may be triggered by a variety of different events.For example, the data may be transmitted periodically, upon detection ofan event (e.g., completion of an analysis or end of a procedure), upondetection of an event defined by a rule (e.g., a user-defined rule),upon receiving user input triggering the transmission, or upon receivinga data request from transformative processing engine 108. Eachtransmission can include, e.g., a single record pertaining to a singleentity, object, procedure, or analysis or multiple records pertaining tomultiple entities, objects, procedures, or analyses.

In some examples, at least some of one or more user devices 104 areassociated with facility 110. In some examples, at least some of one ormore user devices 104 need not be associated with facility 110 or anyother facility. Similar to one or more components 102, one or more userdevices 104 may be capable of receiving, generating, processing, and/ortransmitting data. Examples of one or more user devices 104 include, forexample, a computer, a mobile device, a smart phone, a laptop, anelectronic badge, a set-top box, a thin client device, a tablet, apager, and other similar user devices). One or more user devices 104 maybe configured to run one or more applications developed for interactingwith data collected by transformative processing engine 108. Forexample, those user devices of one or more user devices 104 that are notassociated with facility 110 may be configured to run one or morethird-party applications that may rely in part on the data gathered bytransformative processing engine 108.

Each of one or more components 102 and one or more user devices 104 maybe utilized by one or more users (not shown). Each of the one or moreusers may be associated with one or more clients. For example, one ofthe one or more users can be associated with a client as a result ofbeing employed by the client, physically located at a location of theclient, being an agent of the client, or receiving a service from theclient.

In some examples, one or more components 102 and one or more userdevices 104 may communicate with transformative processing engine 108and management engine 106 via different information formats, differentproprietary protocols, different encryption techniques, differentlanguages, different machine languages, and the like. As will bediscussed with reference to FIG. 2, transformative processing engine 108is configured to receive these many different communications from one ormore components 102, and in some examples from one or more user devices104, in their native formats and transform them into any of one or moreformats. The received and/or transformed communications can betransmitted to one or more other devices (e.g., management engine 106,an entity device, and/or a user device) and/or locally or remotelystored. In some examples, transformative processing engine 108 receivesdata in a particular format (e.g., the HL7 format) or conforming to anyother suitable format and/or is configured to transform received data toconform to the particular format.

One or more components 102 of facility 110 can include and/or has accessto a local or remote memory for storing generated data. In someexamples, the data is stored by one or more servers local to facility110. The record service can be granted access to the data generatedand/or transmitted by one or more components 102. In some examples, therecord service includes a server or a plurality of servers arranged in acluster or the like. These server(s) of the record service can processand/or store data generated by one or more components 102. For example,one or more records can be generated for each entity (e.g., each recordcorresponding to a different entity or being shared across entities).Upon receiving a communication with data from a component (or facility),the record service can identify a corresponding record and update therecord to include the data (or processed version thereof). In someexamples, the record service provides data to transformative processingengine 108.

Irrespective of the type of facility, facility 110 may update data,maintain data, and communicate data to transformative processing engine108. At least some of the data may be stored local to facility 110.

A user interacting with a user device 104 can include, for example, aclient customer, client agent and/or a third party. A user may interactwith user device 104 and/or component 102 so as to, for example,facilitate or initiate data collection (e.g., by a component 102),provide data, initiate transmission of a data request, access dataand/or initiate transmission of a data-processing or data-storageinstruction. In some instances, one or more user devices 104 may operateaccording to a private and/or proprietary network or protocols. In otherexamples, one or more user devices 104 may operate on public networks.In any case, however, transformative processing engine 108 can haveaccess to the one or more components and can communicate with them via apublic, private, and/or proprietary network or protocols. The use of oneor more private and/or proprietary protocols can promote secure transferof data.

Referring next to FIG. 2, a block diagram of an example of aninteraction system 200 is shown. Interaction system 200 includes atransformative processing engine 202. Transformative processing engine202 is an example of transformative processing engine 108 discussed withreference to FIG. 1. Interaction system 200 also includes one or moregeneration components 204. In particular, one or more generationcomponents 204 include an equipment component 206, a lab systemscomponent 208, a temporal component 210, and other generation component212. One or more generation components 204 are examples of one or morecomponents 102 discussed with reference to FIG. 1. In some examples, thedata may pass to the transformative processing engine 202 via aninformation exchange service bus 236 (e.g., an enterprise service bus).In some examples, only a portion of the is passed via the informationexchange service bus 236, while other portions are passed directly tothe transformative processing engine 202 without first passing over theinformation exchange service bus 236.

Generally, one or more generation components 204 includes any suitabledevice or system capable of generating data in the context of aninteraction system. For example, the other generation component 212 mayinclude a sensor on a door, and equipment component 206 may include asophisticated computer-controlled laser device. In either case, eachgeneration component generates some type of data. For example, the dataprovided by the sensor may be used to address security concerns orassessing heating, ventilating, and air conditioning (HVAC) costs for aninstitution. The data provided by the laser device may have beenprovided while engaged in a procedure and may then be used by otherentities in the future to decide how to use the device.

As discussed in further detail herein, data generated by one or moregeneration components 204 can be of a variety of formats, some of whichmay be proprietary. For example, a single component can generate data inmultiple formats, different components can generate data in differentformats, and/or different component types can result in generation ofdata in different formats. In some instances, formatting of a data candepend on a service having been provided, a user initiating datageneration, a destination to receive the data, a location at which aservice was provided, etc. In some examples, a typical interactionsystem includes thousands of generation components producing data inhundreds of formats. In order to harness the power that comes from sucha large amount of data to make informed decisions, it is desirable thatall, or at least a large portion of the data, is shared. Use oftransformative processing engine 202 in accordance with techniquesdescribed herein may achieve this design—making large amounts of data,in many different originating formats available to various types ofusers, via one or more interfaces. At least a portion of the datagenerated by the generation components 204 may be provided to thetransformative processing engine 202. In some examples, each generationcomponent 204 includes an agent that executes on the generationcomponents 204 and determines which data to send to the transformativeprocessing engine 202 and other engines described herein. In someexamples, the generation components 204 provide data to thetransformative processing engine 202 via a messaging bus (e.g., aninformation exchange service bus 236). The messaging bus, which may beincluded in the transformative processing engine 202 or separate, isable to see data that moves throughout the interaction system 200. Theinformation exchange service bus 236 also includes a subscriptionregistry that can be used to manage subscriptions to the informationexchange service bus 236 for certain data (e.g., data having certaincharacteristics). The information exchange service bus 236 may sendand/or direct data to certain other entities when appropriate asindicated by subscription records in the registry.

While one or more generation components 204 are illustrated adjacent toeach other, it is understood that each may be located within onefacility or that the components may be spread out among many facilities.In addition, in some examples, one or more generation components 204belong to different clients.

Turning now to equipment component 206, this component includes anymachine, contrivance, implant, or other similar related article, that isintended to aid in reaching a particular objective. In some instances,equipment component 206 includes one or more sensors to detectenvironmental or other stimuli. Equipment component 206 can include, forexample, equipment to monitor a stimulus, detect stimulus changes,detect stimulus-indicative values, and so on. Exemplary equipmentcomponents 206 include an imaging device, a device that detects andcharacterizes electrical signals, a device that detects pressure, and/ora device that detects concentration of one or more particular elements,compounds and/or gases.

As illustrated, equipment component 206 includes transformative adaptor216. In some examples, transformative adaptor 216 is a device thattransforms, translates, converts, or otherwise adjusts output data fromequipment component 206. For example, an equipment component 206 can bea scanner that outputs its results in format A, but the majority ofother scanners in the interaction system output their results in formatB. Transformative adaptor 216 may be implemented to convert or otherwiseadjust the results in format A to conform closer to format B. Forexample, the conversion from format A to format B may be performed usinga conversion rule, which may be user-define or learned. Transformativeprocessing engine 202 may perform similar tasks as it relates to alldata generated within interaction system 200. In this manner,transformative adaptor 216 can perform an initial step in the process oftransformation, translation, conversion, or adjustment of the output ofequipment component 206. In some examples, transformative adaptor 216 isimplemented in hardware, software, or any suitable combination of both.In some examples, other transformative adaptors (not shown) may beimplemented within others of one or more generation components 204. Insome examples, equipment component 206 may not include transformativeadaptor 216.

Lab systems component 208 includes any suitable laboratory equipment orsystem that is intended to analyze material, such as biologicalmaterial. This includes, for example, laboratory equipment that analyzesbiological samples; electric microscopes; ultracentrifuges; datacollection devices, including Kymographs, sensors connected to acomputer to collect data; monitoring devices; computers used to reportresults of lab tests, and other similar laboratory equipment. Each ofthe above-listed components generates data that is provided (directly orindirectly) to transformative processing engine 202.

Temporal component 210 may include any suitable computing devices usedwith respect to interaction system 200. For example, temporal component210 can be configured to allocate a resource to a particular entityduring a particular temporal window. Temporal component 210 can monitora schedule for the resource and can identify one or more availabletemporal windows that may be secured by a particular entity. Uponreceiving an indication, temporal component 210 may update a schedule ofa resource to reflect that a particular temporal window is to beallocated for service of a particular entity.

Each of one or more generation components 204 and the user device 228may include individual and/or shared storage systems, one or moreprocessors, a user interface, a network connectivity device, and one ormore ports. The storage system include memory that may be implemented,e.g., using magnetic storage media, flash memory, other semiconductormemory (e.g., DRAM, SRAM), or any other non-transitory storage medium,or a combination of media, and can include volatile and/or non-volatilemedia. The storage systems may also be configured to storecomputer-executable code or instructions for interacting with the userinterface and/or for one or more applications programs, such as anapplication program for collecting data generated by the particulargeneration component.

The one or more processors may be configured to access the operatingsystem and application programs stored within the storage systems, andmay also be configured to execute such program code. The one or moreprocessors can be implemented as one or more integrated circuits, e.g.,one or more single-core or multi-core microprocessors ormicrocontrollers, examples of which are known in the art. In operation,the one or more processors can control the operation of the particularcomponent. The one or more processors may access and execute the programcode and at any given time.

The user interface can include any combination of input and outputdevices. In some instances, a user can operate input devices of the userinterface to invoke the functionality of the particular component oruser device. For example, the user interface may enable the user toview, hear, and/or otherwise experience output from component or userdevice via the output devices of the user interface. Examples of outputdevices include a display, speakers, and the like.

The network connectivity device may enable the component or user deviceto communicate with transformative processing engine 202 and othercomponents or other user devices via one or more networks. The one ormore networks may include any suitable combination of cable, cellular,radio, digital subscriber line, or any other suitable network, which maybe wired and/or wireless. In some examples, the network connectivitydevice may enable the component or the user device to communicatewirelessly with various other components and/or transformativeprocessing engine 202. For example, the components may include circuitryto enable data communication over a wireless medium, e.g., usingnear-field communication (NFC), Bluetooth Low Energy, Bluetooth® (afamily of standards promulgated by Bluetooth SIG, Inc.), Zigbee, Wi-Fi(IEEE 802.11 family standards), or other protocols for wireless datacommunication.

The one or more ports may enable the component or the user device toreceive data from one or more sensors. The sensors may be any suitabletype of sensor to capture data. Such captured data may be shared withtransformative processing engine 202 in accordance with techniquesdescribed herein. In some examples, the sensors may also be configuredto detect the location and other details about the component or the userdevice. In some examples, the component and the user device may includeglobal positioning chips that are configured to determine a geolocation.

Transformative processing engine 202 includes an aggregation engine 218,an interoperability engine 220, an access management engine 222, aninterface engine 224, and a data store 226. Generally aggregation engine218 is configured to collect data from multiple communications. The datamay be from one or multiple generation components 204 and/or may be ofsame or different formats. Aggregation engine 218 may be configured toperform one or more operations on the collected data. For example,aggregation engine 218 may tag data, log data, perform protocolconversion, and may support one-to-many communications. The collectionmay be asynchronous. In some examples, the data has been saved locallyin connection with one or more generation components 204 in manydifferent formats having many different data structures.

Aggregation engine 218 can identify data to be aggregated based on, forexample, intra-communication data, a current time, a source generationcomponent, and/or one or more aggregation rules. For example, anaggregation rule may specify that data is to be aggregated across allcommunications that include content with a same entity identifier. Anaggregation may be dynamic. For example, aggregated data may reflectthat from within a most recent 12-hour period. Thus, an aggregation maybe updated in time to exclude older data from the aggregation and toinclude newer data.

Aggregation engine 218 can be configured to provide data from one ormore communications to interoperability engine 220. Interoperabilityengine 220 can be configured to perform one or more operations on thereceived data and store it in data store 226. For example,interoperability engine 220 may perform semantic tagging and indexing ofdata. This may include extracting field values from data, categorizingdata (e.g., by type of data, characteristic of an entity, location offacility, characteristic of facility, and the like), anonymizing orpartially-anonymizing data, and the like. Interoperability engine 220may also include a high availability cache, an alerts engine, and arules engine. In some examples, interoperability engine 220 operatessynchronously.

From interoperability engine 220, data flows to data store 226. Datastore 226 (and any other data store discussed herein) may include one ormore data stores, which may be distributed throughout two or moredifferent locations (e.g., present on different devices, which caninclude devices of different entities and/or a cloud server). In someexamples, data store 226 includes a general data store 230, anoperational data store 232, and an entity-based data store 234. Withineach of the data stores 230, 232, and 234 is stored data. Depending onthe structure of the particular data store, certain data stores mayinclude rules for reading and writing. The data stores 230, 232, and 234may include records, tables, arrays, and the like, which may berelational or non-relational. Depending on the data store, records forindividual entities, business and analytics information, output datafrom one or more generation components 204, and the like may beretained. The data within the data stores 230, 232, and 234 includeelements or tags such that a particular data (e.g., for a single entity,protocol, etc.) can be retrieved.

Access management engine 222 is configured to manage access to featuresof transformative processing engine 202, including access to the dataretained in data store 226. For example, access management engine 222may verify that a user device such as user device 228 is authorized toaccess data store 226. To verify the user device 228, access managementengine 222 may require that a user of the user device 228 input ausername and password, have a profile associated with the interactionsystem, and the like. Access management engine 222 may also verify thatthe user device 228 has an IP address or geographical location thatcorresponds to an authorized list, that the user device 228 includes aplug-in for properly accessing the data store 226, that the user device228 is running certain applications required to access the data store226, and the like.

Interface engine 224 is configured to retrieve the data from data store226 and provide one or more interfaces for interacting with elements oftransformative processing engine 202. For example, interface engine 224includes an interface by which an application running on user device 228can access portions of data within data store 226.

As described herein, an information exchange engine 238 shares a networkconnection with the information exchange service bus 236. Theinformation exchange engine 238 is configured to monitor data (e.g.,messages) that is passed over the information exchange service bus 236and, from the monitored data, select certain portions to provide to oneor more authorized user devices. The information exchange engine 238 isalso configured to route inbound messages and route outbound messages,as described herein. The information exchange engine 238 is alsoconfigured to generate customized messages based on dependent user data.

Turning next to FIG. 3, an architecture stack 300 is shown. In someexamples, techniques relating management of data are implemented inaccordance with architecture stack 300. And while architecture stack 300is illustrated as having a particular structure, it is understood thatother structures, including those with more or less layers thanillustrated, is within the scope of this specification. In someexamples, architecture stack 300 is implemented across an interactionsystem having a plurality of systems belonging to the same client orspread across different clients. Thus, architecture stack 300 can beused to integrate different systems of different organizations,entities, and the like and to provide a fluid sharing of informationamong elements within the interaction system and without the interactionsystem. In some instances, a multi-layer part of architecture stack 300is implemented at a single system or device within an interactionsystem.

The different layers of architecture stack 300 will be describedgenerally with reference to FIG. 3 and in detail with reference tosubsequent figures. Architecture stack 300 includes a receiving layer302 as the bottom-most layer. Receiving layer 302 includes receivingdata from elements that share data with other elements within anaggregation layer 304. For example, as detailed herein, receiving layer302 can include receiving data from generation components that generatedata. As such, receiving layer 302 is where data that has been createdis received. In some examples, the data within receiving layer 302 maybe in its raw formats. The output may then be transmitted to aggregationlayer 304. In some examples, components of receiving layer 302 may havecomplimentary layers to facilitate data transfer. For example, thecomponents may include a data generation and/or a data transmissionlayer for providing data to receiving layer 302.

Elements of aggregation layer 304 aggregate the data generated by theelements of receiving layer 302. For example, the elements ofaggregation layer 304 may include aggregation engines that collect datafrom generation components located within receiving layer 302. Suchaggregation may be performed periodically, in response to a userrequest, according to a schedule, or in any other suitable manner. Insome examples, data of aggregation layer 304 may be aggregated accordingto input and/or rules and may aggregate across records pertaining to,e.g., a facility, entity, time period, characteristic (e.g., demographiccharacteristic or condition), outcome, and any other suitable inputand/or rules. The aggregation may include compiling the data, generatinga distribution, generating a statistic pertaining to the data (e.g.,average, median, extremum, or variance), converting the data,transforming the data to different formats, and the like.

Next, architecture stack 300 includes an active unified data layer 308.Elements of active unified data layer 308 receive data from the elementsof the other layers and store such data in a unified manner. In someexamples, this may include storing the data in a manner that allows forlater searching and retrieval using a defined set of method calls,techniques, and or procedures. For example, the data may be stored suchthat a different application can access the data in a standard orunified manner. Thus, elements of active unified data layer 308 mayreceive information collected or generated within aggregation layer 304and make certain adjustments to the data (e.g., translations, tagging,indexing, creation of rules for accessing the data, conversion offormatting of the data, generation of compressed versions, and the like)prior to retaining the data within one or more data stores accessiblewithin active unified data layer 308.

Architecture stack 300 also includes an access management layer 310,which can include an audit/compliance layer 312 and/or an agency layer314. Access management layer 310 includes elements to manage access tothe data. For example, access management layer 310 may include elementsto verify user login credentials, IP addresses associated with a userdevice, and the like prior to granting the user access to data storedwithin active unified data layer 308.

Audit/compliance layer 312 includes elements to audit other elements ofarchitecture stack 300 and ensure compliance with operating procedures.For example, this may include tracking and monitoring the other elementsof access management layer 310.

Agency layer 314 includes an access location (e.g., a virtual privatenetwork, a data feed, or the like) for elements of agencies that areinterested in the operations of the interaction system in whicharchitecture stack 300 is implemented. For example, agency layer 314 mayallow a governmental entity access to some elements within architecturestack 300. This may be achieved by providing the governmental entity adirect conduit (perhaps by a virtual private network) to the elements ofaccess management layer 310 and the data within active unified datalayer 308. Audit/compliance layer 312 and agency layer 314 aresub-layers of access management layer 310.

Architecture stack 300 also includes interface layer 316. Interfacelayer 316 provides interfaces for users to interact with the otherelements of architecture stack 300. For example, clients, entities,administrators, and others belonging to the interaction system mayutilize one or more user devices (interacting within application/devicelayer 320) to access the data stored within active unified data layer308. In some examples, the users may be unrelated to the interactionsystem (e.g., ordinary users, research universities, for profit andnon-profit research organizations, organizations, and the like) and mayuse applications (not shown) to access the elements within architecturestack 300 via one or more interfaces (e.g., to access data stored withinactive unified data layer 308). Such applications may have beendeveloped by the interaction system or by third-parties.

Finally, architecture stack 300 includes application/device layer 320.Application/device layer 320 includes user devices and applications forinteracting with the other elements of architecture stack 300 via theelements of interface layer 316. For example, the applications may beweb-based applications, entity portals, mobile applications, widgets,and the like for accessing the data. These applications may run on oneor more user devices. The user devices may be any suitable user deviceas detailed herein.

Turning next to FIG. 4, a diagram 400 is shown that depicts a portion ofarchitecture stack 300 according to at least one example. In particular,the diagram 400 includes receiving layer 302, aggregation layer 304,aggregation layer 306, and a portion of active unified data layer 308.Receiving layer 302 receives data from one or more components 410-418.Components 410-418 are examples of one or more generation components204. Components 410-418 may be spread across multiple facilities withina single or multiple clients. In some examples, components 410-418 mayinclude complimentary layers to facilitate data transmission. Forexample, components 410-418 may include a transmission layer, generationlayer, and/or a receiving layer to communicate data at receiving layer302 and, in some examples, receive data from receiving layer 302.

In some instances, two or more of components 410-418 generate dataaccording to different formats. The data can then be transformed,translated, or otherwise adjusted before an aggregation engine 420(e.g., aggregation engine 218) or a third-party aggregation engine 422(e.g., aggregation engine 218) collects the data. In some examples, theadjustment takes place within receiving layer 302. Thus, an adaptor 424is associated with component 412 located in receiving layer 302. Adaptor424 is an example of transformative adaptor 216. Adaptor 424 isimplemented, as appropriate, in hardware, software, or any suitablecombination of both. For example, transformative adaptor 216 may be abolt-on adaptor that adjusts data as such data leaves component 412.

Other adaptors, such as adaptor 426 and adaptor 428, are implementedwithin aggregation layer 304. These adaptors can function in a similarmanner as adaptor 424. In some examples, the data provided by component414 is transmitted through adaptor 426 prior to being directed toaggregation engine 420. The data provided by component 416 istransmitted through aggregation layer 304 and/or enters aggregationengine 420 without having first traveled through an adaptor. The dataprovided by component 418 is transmitted through aggregation layer 304and through adaptor 428. In some examples, component 418 provides forstreaming of data. The data provided by component 410 is transmitteddirectly to third-party aggregation engine 422.

Aggregation engine 420 and third-party aggregation engine 422 functionin a similar manner. In some examples, third-party aggregation engine422 is operated by a different entity than the entity that operatesaggregation engine 420 and may belong to different clients or adifferent interaction system. This may be because the data collected bythird-party aggregation engine 422 differs in some way from the datacollected by aggregation engine 420. In any event, aggregation engine420 is configured to perform integration of data, including genericintegration. For example, aggregation engine 420 performs one or moreoperations on data including tagging, logging, and protocol conversion.Aggregation engine 420 also supports one-to-many communications of data.In some examples, data flows between aggregation engine 420, thethird-party aggregation engine 422, and some of components 410-418 andelements of active unified data layer 308.

The diagram 400 also includes the information exchange service bus 236and the information exchange engine 238. As introduced herein, messagespassing through the aggregation layer 304 can pass over the informationexchange service bus 236. In this manner, the information exchangeengine 238 can access the messages, route the messages, and/or customizethe messages.

Referring next to FIG. 5, a diagram 500 is shown that depicts a portionof architecture stack 300 according to at least one example. Inparticular, diagram 500 includes active unified data layer 308 and aportion of access management layer 310. Active unified data layer 308,as illustrated in diagram 500, includes an interoperability engine 502(e.g., interoperability engine 220), a collection engine 504, a datastore integrity engine 506, and a data store 508 (e.g., data store 226).Generally, interoperability engine 502 receives data from elementswithin aggregation layer 304 (e.g., from aggregation engine 420) andperforms one or more operations with respect to the data.Interoperability engine 502 also facilitates storage of at least aportion of the processed information in data store 508.

Collection engine 504 is configured to generate message indicatorsidentifying flows of data by and between elements of an interactionsystem implemented using the techniques described herein. The flows ofinformation include messages which include data, and the messageindicators include unique message identifiers that can be used toidentify the messages. The unique message identifiers includeinformation that can be used to uniquely identify the messages. Forexample, a unique message identifier for a particular message caninclude a concatenation of the following information stored in a table:a source application, a facility, a message type, and a message controlidentification (ID). The unique message identifier can also be themessage control ID. The unique message identifier may be created asmessages including data are transmitted from aggregation layer 304.

In some examples, the table also includes information for tracking theprogress of the message from an origination node to a destination node.For example, typically when a message (e.g., any communication of data)is first received by transformative processing engine 108 (e.g.,interoperability engine 502), management engine 106 (e.g., collectionengine 504 of management engine 106) may generate a unique identifierfor the message in order to track that message as it moves throughoutthe interaction system. The unique identifier may be included in theheader of the message such that when the next node (e.g., component,device, server, etc.) after transformative processing engine 108receives the message, that node can report back to management engine 106that it saw the message. In this manner, management engine 106 may trackmessages from end-to-end for the life of the message.

In one example, the messages are requests. The requests may be generatedbased om user input at one of the components. The requests may bereceived by transformative processing engine 108 and integrated into thesystem. In some examples, management engine 106 may be notified that therequests have been received and may therefore be configured to generatemessage IDs for each request. These message IDs may then be associatedwith each of the requests. As the requests continue to move throughoutthe interaction system (e.g., away from transformative processing engine108), management engine 106 may track their movement using the messageIDs. If one of the requests does not arrive at its destination,management engine 106 may determine why the request was stopped. In someexamples, this cause may be hardware related (e.g., an unpluggedEthernet cable, a broken router, etc.), software related (e.g., a routerrouting to the wrong location), or any other reason for orders notarriving at their correct destination.

In some examples, management engine 106 (e.g., collection engine 504 ofmanagement engine 106) may receive the message and/or message identifierdirectly from one of components 410-418. For example, one of components410-416 may be configured to generate the unique message identifierand/or communicate directly with management engine 106. The message alsomay travel via one or more intermediate nodes on its way to thedestination node. In some examples, a node is a component such ascomponents 410-418, which may be running an application. In someexamples, the unique identifier and the routing of the message to itsdestination may be stored in a table that also includes: a geolocationof each node, a network from which the message originated, a type ofnode, the unique node identifier, and a time associated with the messageleaving the origination node. In some examples, collection engine 504provides unique message identifiers to other elements of the interactionsystem to monitor the messages as they move throughout the interactionsystem. Collection engine 504 also provides a portion of the uniquemessage identifiers to a management platform (indicated by a circle 528)for further analysis of the message identifiers. Such analyses mayinclude reconciliation of lost messages, latency reporting, auditmanagement and compliance, and other such analyses.

As mentioned previously, interoperability engine 502 is configured tostore data in data store 508. A plurality of sub-engines 510-516 ofinteroperability engine 502 are configured to perform operationsrelating to storing data in data store 508.

Interoperability engine 502 includes a tagging engine 510 configured toperform semantic tagging and indexing of data. Tagging engine 510therefore is configured to receive data, read metadata associated withthe data, semantically scan the content of the data, and associate oneor more tags with the data. Tagging engine 510 may therefore have accessto hundreds, thousands, or even more possible tags. These tags may havebeen input by users, learned, pre-defined, generated by outsidethird-party mapping sources, and/or gathered from other componentsand/or data stores of the interaction system. For example, if the datais a chart for an entity, the tagging engine may be configured to readany metadata associated with the chart to determine which tags may beappropriate to associate with the chart. From the metadata, taggingengine 510 may determine that the chart is for a type of entity byreading metadata indicating that an author field is populated with thename of another particular type of entity. Tagging engine 510 may haveaccess to other data to compare the analyzed metadata against (e.g., toidentify that the author's name corresponds to Dr. Brown who is anoncologist). Other examples, of metadata that may be included in one ormore fields include author, document type, creation time and date, lastupdate time and date, upload time and data, geographic location, uniqueID associated with the client or facility where the data originated, andother similar fields. The tags may be stored in association with thedata (e.g., the chart) and/or may be stored independent from the databut include an identifier such that when searching tags the data may becapable of population.

Continuing with the example from above, if the data is a chart for afirst type of entity, tagging engine 510 may be configured to read thecontent of the chart to determine which tags may be appropriate toassociate with the chart. For example, this may comprise analyzing thecontent of the chart (i.e., individual pages) semantically to look forartifacts (e.g., keywords, phrases, and the like) in the content. Theseartifacts may be identified by tagging engine 510 and used to decidewhich tags to associate with the document. In some examples, semanticscanning may involve filtering out words (e.g., articles, such as “a”and “the”), phrases, and the like. Similar to the reading of metadata,the tags may be pre-defined, user-defined, learned, and the like. Insome examples, reading metadata associated with messages may providemeaning and/or give context to the particular record of data. Thismeaning and/or context may assist tagging engine 510 to determine one ormore tags to associate with the data. The tags may be chosen, forexample, based on values of particular fields in the data, detecting afrequency of one or more words in a document or metadata and/or of a setof related words (e.g., tagging a record with “cancer” upon detectingwords such as tumor, metastasize, chemotherapy, radiation, oncology,malignant, stage 3, etc.). In this manner, tagging engine 510 may alsoindex portions of the data within one or more data stores of data store508. In some examples, such indexing may be based in part on theselected tags.

Interoperability engine 502 also includes a reports engine 512configured to generate one or more reports or alerts based on data. Forexample, reports engine 512 may generate reports when certain types ofdata are received or when data with certain characteristics is received.Reports engine 512 may also generate alerts. The reports and/or alertsgenerated by reports engine 512 may be outputted in the form of one ormore communications to an administrator, an authorized user, or othersimilar user via a user device. Such communications can include, forexample, signals, sirens, electronic notifications, popups, emails, andthe like. Content of such communications may include informationcharacterizing a performance metric, efficiency and/or outcomes;identifying concerning patterns; identifying losses of data; and thelike. In some examples, the content is presented in the form of one ormore documents, tables, figures, charts, graphs, and the like.

Interoperability engine 502 also includes a rules engine 514 configuredto create and manage condition-response rules, alert/reports rules,data-formatting rules, data-sharing rules, transmission rules,aggregation rules, user authorization rules, and other similar rules.Such rules may be user-defined, fixed, learned by elements of theinteraction system, and any combination of the foregoing. Finally,interoperability engine 502 includes an application engine 516configured to provide service-oriented architecture web services.

Data store 508 includes an electronic record information data store 518(“ERI data store 518”), a general data store 520, an operational datastore 522, an entity-based data store 524, and a streaming cachingstorage 526. While data store 508 is illustrated as including a fixednumber of data stores and storage elements, it is understood that datastore 508 can include any suitable number of data stores and storageelements, including more than illustrated or less than illustrated.

In some examples, a data query script is provided to query a first datastore and/or to obtain data for populating a data store. Such scriptcould query a data store described herein (e.g., data store 508) and/orcould be used to obtain data to populate a data store described herein(e.g., data store 508). In one instance, the script is configured to berepeatedly executed, so as to repeatedly draw data from a source datastore. The retrieved data can then be formatted, filtered, sorted and/orprocessed and then stored, presented and/or otherwise used. In thismanner, the script can be used to produce streaming analytics.

In some instances, the data query script, when executed, identifies eachof the data stores of interest. Identifying the data stores of interestinvolves identifying at least a portion of data from the data storessimultaneously and/or sequentially. For example, the script can identifycorresponding data stores (e.g., or components of a single data store ormultiple data stores) that pertain to one or more similar variables butthat differ in one or more other variables. Once the portion of the datafrom the data stores is identified, a representation of the identifieddata can be output to one or more files (e.g., Extensible MarkupLanguage (XML) files) and/or in one or more formats. Such outputs canthen be used to access the data within one or more relational databaseaccessible using Structured Query Language (SQL). Queries made using SQLcan be made sequentially or in parallel. Results from an SQL query maybe stored in a separate database or in an XML file that may be updatedeither in part or as a whole. The data query script may be executedperiodically, in accordance with a user-defined rule, in accordance witha machine-defined or machine-learned rule, and in other suitable manner.

Within ERI record data store 518 is retained data. In some examples, theinformation within ERI record data store 518 is organized according toentity identifying information. Thus, ERI record data store 518, in someexamples, includes individually identifiable information. But it mayalso include de-identified information.

Within general data store 520 is retained data. The data may be storedin a relational database format or in any other suitable format. Thus,the data within general data store 520 may be retained in a datastructure that includes one or more tables capable of accessing eachother. In some examples, general data store 520 includes a subset of theinformation that is included in operational data store 522.

Within operational data store 522 is retained data in a relationaldatabase format. Thus, the data within operational data store 522 may beretained in a data structure that includes one or more data structures(e.g., tables) capable of accessing each other. Operational data store522 is an example of an operational data warehouse. In operational datastore 522 is joined many different types of data. In some examples, theoperational data store 522 includes data pertaining to decision makingas discussed herein and other data typically used.

Within entity-based data store 524 is retained data in a non-relationaldatabase format. Thus, the data within entity-based data store 524 maybe retained in a structure other than tables. Such structure may beappropriate for large and complex data sets. In some examples,entity-based data store 524 (or any other data store) may be a unifiedsystem, which may include: a document-centric, schema-agnostic,structure-aware, clustered, transactional, secure, database server withbuilt-in search and a full suite of application services. An example ofsuch a unified system may be Marklogic. Entity-based data store 524 cansupport data aggregation, data organization, data indexing, data taggingand mapping to semantic standards, concept matching, concept extraction,machine learning algorithms, concept discovery, concept mining, andtransformation of record information. In some examples, entity-baseddata store 524 includes data pertaining to decision making (similar togeneral data store 520) as discussed that is organized and accessed in adifferent manner. For example, the data within entity-based data store524 may be optimized for providing and receiving information over one ormore information exchanges. In some examples, entity-based data store524 includes a subset of the information that is included in operationaldata store 522.

Finally, in some examples, streaming caching storage 526 is a streamingdata cache data store. As discussed previously, certain components ofcomponents 410-418 may support streaming data to other components oruser devices. Streaming caching storage 526 is a location wherestreaming data can be cached. For example, assume that component 418 isa piece of equipment operating at Location A and that a user using acomputer in Location B desires to view a live of substantially livestream of outputs of the piece of equipment. Component 418 can send aportion of data to streaming caching storage 526 which can retain theportion of the data for a certain period of time (e.g., 1 day). Thus,streaming caching storage 526 is configured to cache data that can bestreamed.

Diagram 500 also includes data store integrity engine 506. In someexamples, data store integrity engine 506 is configured to ensureintegrity of the information within data store 508. For example, datastore integrity engine 506 applies one or more rules to decide whetherinformation within all or part of data store 508 should be scrubbed,removed, or adjusted. In this manner, confidence is increased that theinformation within data store 508 is accurate and current.

FIG. 6 shows a diagram 600 which depicts a portion of architecture stack300 according to at least one example. In particular, the diagram 600includes access management layer 310, audit/compliance layer 312, agencylayer 314, and a portion of interface layer 316.

Access management layer 310, as illustrated in the diagram 600, includesan access management engine 602. Access management engine 602 is anexample of access management engine 222. Generally, access managementengine 602 can be configured to manage access to elements oftransformative processing engine 202 by different components,applications, and user devices.

Access management engine 602 within access management layer 310 alsoprovides functionality similar to an operating system. For example,access management engine 602 includes a plurality of engines configuredto manage different aspects of interacting with elements of theinteraction system. For example, a user who desires to access portionsof data retained in data store 508, may do so by interacting with accessmanagement engine 602 using one or more applications (not shown). Thus,access management engine 602 includes a variety of engines to enablesuch interaction. The engines include, for example, an authenticationaccess engine 604, a login engine 606, a user preference engine 608, asecurity engine 610, an analytics and search engine 612, a data accessengine 614, an update engine 616, and a streaming data engine 618. Thedifferent engines of access management engine 602 can define routines,protocols, standards, and the like for interacting with elements of theinteraction system.

Beginning first with authentication access engine 604, authenticationaccess engine 604 evaluates the rules and conditions under which usersmay access elements of the interaction system; in particular, theconditions under which users may access data within data store 508.These rules and conditions may be user-defined (e.g., by anadministrator or reviewer), learned over time, and/or may be dynamicallyupdated and/or evaluated based on characteristics of the user or theuser's device attempting to access the interaction system. The rules andconditions may indicate the types of users who have particular types ofaccess within the interaction system. The type of access may also relateto the degree to which data is identified/de-identified. In someexamples, a user desiring access to data provides certain identifyinginformation and authentication access engine 604 authenticates anidentity of the user.

Login engine 606 evaluates the rules and conditions under which usersare able to log in to the interaction system or access applicationsassociated with the interaction system. These rules and conditions maybe user-defined (e.g., by an administrator), learned over time, and alsomay be dynamically updated and/or evaluated based on characteristics ofthe user or the user's device attempting to access the interactionsystem. Thus, while authentication access engine 604 evaluates the rulesto determine which users may access the interaction system, login engine606 evaluates the particular credentials, profiles, etc. of the users.For example, login engine 606 can confirm that an entered username(e.g., and password), provided biometric data or code or identifier in ascanned tag or badge matches that in an authorized user data structure.

Login engine 606 evaluates one or more user profiles associated witheach authenticated user. In some examples, a user profile includes ausername, password, and other information associated with the user. Forexample, a user profile may indicate characteristics about the user.

User preference engine 608 evaluates the rules and conditions underwhich user are able to store and update one or more user preferencescorresponding to access of the interaction system or access toapplications associated with the interaction system. These rules andconditions may be user-defined (e.g., by the user or administrator), andmay include rules for default preferences. For example, using userpreference engine 608, a user may indicate a format in which the userprefers to receive outputted information, display characteristics of agraphical user interface associated with the user, and other similaruser preference settings. For example, the user may indicate thatcertain types of reports and/or alerts are to be sent to the user.

Security engine 610 evaluates the rules and conditions for ensuring thesecurity of access to the elements of the interaction system. In someexamples, these rules and conditions are determined by administrators ofthe interaction system. In some examples, security engine 610 provides aplurality of computer virus protection services. These services can becalled up and implemented when accessing the interaction system oraccessing applications associated with the interaction system. The rulesand conditions may be based on roles, based on profiles, based ondomains, and any other suitable security configuration. For example,because the interaction system may include sensitive data, securityengine 610 may enforce a domain-based rule that protects certainsensitive information (e.g., identifying information).

Analytics and search engine 612 evaluates the rules and conditions underwhich users can search for data within the interaction system and accessanalytics relating to the interaction system. In some examples, theserules and conditions are user-defined or learned over time in accordancewith search engine optimization techniques. For example, analytics andsearch engine 612 is used to search within data store 508 for particulardata. Analytics and search engine 612 supports any conventionalsearching algorithms. For example, search engine 612 can be used tosearch within various fields and potential field values. In someexamples, search engine 612 can provide analytics, such as statistics,graphs, distributions, and/or comparative analysis pertaining toparticular entities and/or characteristics. Such information may beselected by a user and presented on a user interface.

Data access engine 614 evaluates the rules and conditions under whichusers may operation in order to access particular data within data store508. In some examples, these rules and conditions are user-defined orlearned over time. For example, data access engine 614 may indicate theroutines, subroutines, or other logic needed for an application toaccess certain portions of data store 508. For example, whileauthentication access engine 604 and login engine 606 may manage whichusers can access parts of the interaction system, data access engine 614may manage how authenticated users access data within data store 508. Tothis end, data access engine 614 may enforce and/or evaluate certainrules managing how users access different components of the interactionsystem. In some examples, data access engine 614 may be used to actuallyaccess data within data store 508 (e.g., extract, download, or otherwiseaccess). In some examples, data access engine 614 may define procedures,protocols, and the like for accessing data. The protocols and proceduresfor accessing data access engine 614 (like the other engines of accessmanagement engine 602) may be provided to developers in the form of asoftware development kit (SDK). SDKs may enable developers writeapplications that can effectively communicate with elements (e.g., datastore 508) of the interaction system. In particular, applications thatcan access a portion of the data stored within active unified data layer308.

Update engine 616 evaluates the rules and conditions for providingupdates to other engines within access management engine 602, plug-insfor applications that access the interaction system, and for othersimilar elements of the interaction system. For example, updates may begenerated at runtimes, at defined time intervals, upon request by auser, upon receiving a threshold quantity of new or changed data. Oncean update is performed, an interface may be refreshed, a report may besent indicating that the update was successful or unsuccessful, or thelike.

Streaming data engine 618 defines the rules and conditions for enablingstreaming of data between components and user devices of the interactionsystem. For example, streaming data engine 618 may enable component 414to stream data. Streamed data may include live or substantially liveaudio or video feeds, results of tests, output from equipment ordevices, and any other suitable type of data capable of being streamed.In some examples, the data may be streamed to other components or userdevices within the network or outside the network. In order to establisha streaming transmission, streaming data engine 618 may identify astreaming destination and a streaming origin. Next, streaming dataengine 618 may pair the two and enable streaming. This may includeallocated bandwidth within one or more network devices associated withthe interaction system. Streaming data engine 618 may also adjust thequality of the streaming data based on the availability of bandwidth. Insome examples, streaming data engine 618 may receive incoming streams(and continuously present the stream or monitor for particular data(e.g., exceeding a threshold, exhibiting an above-threshold change,having a particular value)).

Within audit/compliance layer 312 is located an access log engine 622.Access log engine 622 evaluates the rules and conditions for loggingaccess to the interaction system by users, applications, devices, andthe like. Logging access includes, in some examples, logging dataconventionally collected by access log engines running in similarenvironments. Access log engine 622 can use this data to generate andtransmit reports, for example, to stakeholders of the interaction systemsuch that they can make informed decisions regarding that is accessingthe interaction system and for what purposes.

Within agency layer 314 is located an agency engine 624. Agency engine624 evaluates the rules and conditions under which agencies can accessthe interaction system. In some examples, agency engine 624 may be usedto track one or more performance indicators identified by a governmentagency and/or to provide report instances of defined types of events. Insome examples, a university is an agency that uses agency engine 624 tocollect data pertaining to one or more studies. Agency engine 624 cancollect the pertinent data, potentially format and/or analyze the data,and facilitate transmission of the data to the appropriate agency.

FIG. 7 shows a diagram 700 which depicts a portion of architecture stack300 according to at least one example. In particular, diagram 700includes interface layer 316, and application/device layer 320. Withininterface layer 316 is located interface engine 702 (e.g., interfaceengine 224). Interface engine 702 is configured to generate one or moreinterfaces (e.g., graphical user interface 726, programmatic interface728, and/or web interface 730) to enable data to flow to user devices710, 712, and 714 via respective applications 720, 722, and 724. In someexamples, the interfaces of interface engine 702 are embodied inhardware, software, or some combination of both. Within interface layer316 communications and inputs directed to interacting with elements ofaccess management layer 310 may be embodied.

Graphical user interface 726 is any suitable graphical user interfaceconfigured to interact with elements of the interaction system.Programmatic interface 728 includes an application programminginterface, a programmatic user interface, and other similar interfacesfor defining core functions for accessing elements of the interactionsystem. For example, programmatic interface 728 may specify softwarecomponents in terms of their operations. Web interface 730 is anysuitable web interface configured to interact with elements of theinteraction system. Any of the interfaces described herein may beconfigured to receive user input, present dynamic presentations thatdepend on user input, and otherwise respond to user input. In someexamples, such input may be provided via one or more input devices(e.g., a keyboard, touchscreen, joystick, mouse, microphone, devicescapable of capturing inputs, and the like) operated by one or more usersof user devices 706-714. Output may be provided via one or more outputdevices (e.g., a display or speaker).

Interface engine 702 is utilized by applications internal to theinteraction system and external to the interaction system to accessdata. In some examples, the applications that are internal includeapplications that are developed for internal use by various entitiesassociated with the interaction system. In some examples, theapplications that are external to the interaction system includeapplications that are developed for external use by those that are notassociated with the interaction system.

Generally, within application/device layer 320, applications 716-724which communicate with other elements of architecture stack 300 usingthe interfaces generated by interface engine 702 are defined. Thisincludes detailing how applications 716-724 are to interact with theinterfaces generated by interface engine 702 for accessing data. Forexample, interacting may include accepting inputs at user devices706-714 to access data and, in response, providing the data, prompts, orother types of interaction with one or more users of the user devices706-714. Thus, applications 716-724 may be related to one or more of theinterfaces generated by interface engine 702. For example, application720 may be interact with a graphical user interface (whether generatedby interface engine 702 or otherwise) to interact with other elements ofthe interaction system. Interacting may include receiving inputs at thegraphical user interface via application 720, providing output data tothe graphical user interface application 720, enabling interaction withother user devices, other applications, and other elements of theinteraction system, and the like. For example, some of the inputs maypertain to aggregation of data. These inputs may include, for example,types of data to aggregate, aggregation parameters, filters ofinterested data, keywords of interested data, selections of particulardata, inputs relating to presentation of the data on the graphical userinterface, and the like. Providing output data may include providing theaggregated data on the graphical user interface, outputting theinformation to one of the other user devices 706-714 running one of theother applications 716-724.

Turning now to the details of applications 720, 722, and 724. In someexamples, applications 720, 722, and 724 include a variety of differentapplications that can be designed for particular users and/or uses. Inone example, application 720 includes dashboards, widgets, windows,icons, and the like that are customized for a particular entity. In someexamples, application 720 may present different data depending on afocus of the entity and protected information associated with theentity. In this manner, application 720 adapts and automatically adjustsdepending on the context in which the entity is using the application.Application 720 may be configured to receive input, adjustpresentations, present unprompted alerts, adjust display of content,move more relevant content to the foreground, move less relevant contentto the background, and/or populate forms for the entity.

In another example, application 722 may be specific for nurses or typesof nurses. In this example, application 722 may include dashboards,widgets, windows, icons, and the like that are customized to individualnurses. Similar to the example discussed above pertaining to the user,in some examples, application 724 may present different data dependingon a position of the nurse. In this manner, application 722 adapts andautomatically adjusts depending on the context in which the nurse isusing the application. For example, the nurse may receive data, such astest results.

In some examples, application 724 may be a multi-role application foradministrators and is used to manage entities constitute the populationof the entities or organizations within the interaction system. Similarto the other examples discussed, in some examples, application 724 maypresent different data depending on a role of the user who is usingapplication 724. In this manner, application 724 adapts andautomatically adjusts depending on characteristics of the user who isusing application 724. In this manner, application 724 can providedifferent data depending on the role of the user. For example, whetherdata presented includes identifiable or de-identified information maydepend on a position of the user.

Applications 716 and 718 shown in connection with interface engine 702are applications developed by third-parties. In some examples, suchapplications include any suitable application that benefits fromaccessing data. The interaction system may include data pertaining tohundreds of thousands of entities. Having data pertaining to so manyentities presents security concerns. For example, much of the data maybe identifying data. Accordingly, data that may be accessed byapplications 716 and 718 may be limited. In some examples, an entity ofthe interaction system may use one of applications 716, 718 to accesshis or her own data. In this example, the identity of the entity may beverified in accordance with techniques described herein.

User devices 706-714 are any suitable user devices capable of runningapplications 716-724. User devices 706-714 are examples of the userdevice 228. In some examples, the user devices include: mobile phones,tablet computers, laptop computers, wearable mobile devices, desktopcomputers, set-top boxes, pagers, and other similar user devices. Insome examples, at least some of user devices 706-714 are the samedevices as at least some of the one or more components 410-418. In someexamples, user devices 706-714 may include complementary layers toapplication/device layer 320 and/or receiving layer 302. For example,user devices 706-714 may include a transmission layer, a generationlayer, and/or a receiving layer to communicate data atapplication/device layer 320 and at receiving layer 302.

Turning now to FIG. 8, an interaction system 800 is shown according toat least one example. Interaction system 800 includes an internalorganization 822 including a transformative processing engine 802. Thetransformative processing engine 802 is an example of transformativeprocessing engine 202 previously discussed. Interaction system 800 isillustrated as an example configuration for implementing the techniquesdescribed herein. In particular, a configuration of elements asillustrated in FIG. 8, at least in some examples, communicates accordingto the layers of architecture stack 300. For example, internalorganization 822 includes generation components 804(1), 804(2), and804(N) which provide data to aggregation servers 806(1)-806(N).

Generation components 804(1), 804(2), and 804(N) operate in accordancewith receiving layer 302. In some examples, generation component 804(1)is a piece of equipment, generation component 804(2) is computer with adata collection device, a type of lab system, and generation component804(N) is a terminal. Aggregation servers 806(1)-806(N) operate inaccordance with aggregation layer 304. Aggregation servers 806(1)-806(N)share data with data storage servers 808(1)-808(N) via one or moreinternal network(s) 810. In some examples, internal network 810 is anysuitable network capable of handling transmission of data. For example,internal network 810 may be any suitable combination of wired orwireless networks. In some examples, internal network 810 may includeone or more secure networks. Data storage servers 808(1)-808(N) areconfigured to store data in accordance with active unified data layer308. Data storage servers 808(1)-808(N) include database servers, filestorage servers, and other similar data storage servers.

Access management servers 812(1)-812(N) manage access to the dataretained in the data storage servers 808(1)-808(N). Access managementservers 812(1)-812(N) communicate with the other elements of interactionsystem 800 via internal network 810 and in accordance with accessmanagement layer 310.

Interface servers 814(1)-814(N) provide one or more interfacesapplications to interact with the other elements of interaction system800. Interface servers 814(1)-814(N) provide the one or more interfacesand communicate with the other elements of interaction system 800 viainternal network 810 and in accordance with interface layer 316. Theinterfaces generated by the interface servers 814(1)-814(N) can be usedby internal user devices 816(1)-816(N) and external user devices 818(1),818(2), and 818(N) to interact with elements of interaction system 800.

Internal user devices 816(1)-816(N) are examples of user devices706-714. In some examples, internal user devices 816(1)-816(N) runapplications via the interfaces generated by interface servers814(1)-814(N). As an additional example, external user devices 818(1),818(2), and 818(N) can run applications developed by third parties thataccess the other elements of interaction system 800 via the interfacesgenerated by interface servers 814(1)-814(N).

External user devices 818(1), 818(2), and 818(N) access the interfacesvia external network 820. In some examples, external network 820 is anunsecured network such as the Internet. External user devices 818(1),818(2), and 818(N) are examples of user devices 706-714. External userdevice 818(1) is a mobile device. In some examples, the mobile devicemay be configured to run an application to access interaction system800. Similarly, the other external user devices 818(2)-818(N) runapplications that enable them to access interaction system 800. Whileinteraction system 800 is shown as implemented using discrete servers,it is understood that it may be implemented using virtual computingresources and/or in a web-based environment.

The environments, systems, networks, models, and the like of FIGS. 1-8may be used to implement the techniques described herein with referenceto FIGS. 9-19. For example, a processing engine is provided thatcommunicates with local servers in connection with wireless signalstransmitted and received by mobile wireless transceivers and mountedwireless transceivers. The processing engine may assess the completionof events. For example, the processing engine may track entities toanalyze compliance with protocols and, in some instances, may modify theprotocols themselves to improve compliance and/or meet the changingneeds of a facility. The protocols may ensure that the facility complieswith federal, state, industry, and/or organization requirements.

FIG. 9 illustrates a system 900 for assessing completion of events,according to several embodiments of the present disclosure. System 900may include a platform 905 that has a plurality of applicationprogramming interfaces (APIs) and/or modules that communicate with aprocessing engine 950. For example, platform 905 may include anidentifier API 910, a temporal API 915, an entry API 920, an arrivaldata API 925, natural language understanding modules 930, a review API935, a learning/knowledgebase API 940, and a rules API 945. IdentifierAPI 910, temporal API 915, entry API 920, arrival data API 925, naturallanguage understanding modules 930, review API 935,learning/knowledgebase API 940, and rules API 945 may be housed withininterface layer 316 discussed previously. Platform 905 may be hosted ina web-based environment or through cloud computing.

Platform 905 may communicate with various external components, such asan information data store 955, a temporal data store 960, an accesspoint data store 965, an other data store 970, an object data store 985,a structured query language (SQL) data store 990, a rules data store995, a user and reporting interface 975, a component 977, and aconversational computing interface 980. Information data store 955,temporal data store 960, access point data store 965, other data store970, object data store 985, SQL data store 990, and rules data store 995may be examples of ERI record data store 518, general data store 520,operational data store 522, entity-based data store 524, and/orstreaming caching storage 526. User and reporting interface 975 andconversational computing interface 980 may be examples of user device104. Component 977 may be an example of component 102.

Identifier API 910 may request and receive information about an entityfrom information data store 955. The information may include anidentifier of the entity, such as an RFID tag number. Temporal API 915may request and receive information about chronologies of entities at afacility from temporal data store 960. Entry API 920 may request andreceive information about entries of entities at controlled accesspoints within the facility from access point data store 965. Arrivaldata API 925 may request and receive information about other entitieswho access the facility from uncontrolled access points from other datastore 970. The information may include identifying information about theother entities and a date and/or time of arrival of the other entities.

A user may utilize user and reporting interface 975 and/orconversational computing interface 980 to provide information about thecompletion or non-completion of an event, such as compliance ornon-compliance with a protocol. The information may include data aboutone or a plurality of components that make up the event. The user mayaccess user and reporting interface 975 and/or conversational computinginterface 980 via any suitable device, such as a computer or asmartphone. User and reporting interface 975 may include a web-basedinterface, and conversational computing interface 980 may include ashort message service (SMS) interface. User and reporting interface 974and/or conversational computing interface 980 may automatically detectan identifier of the user and a chronology of the input.

Component 977 may determine the identifier and the location of anentity, as described in further detail below. The location of the entitymay be determined at a plurality of times. For example, component 977may include a mobile wireless transmitter and/or a mounted wirelesstransmitter. The mobile wireless transmitter may be integrated with acomputer, a mobile device, a smart phone, a laptop, an electronic badge,an RFID tag, a tablet, or a pager. The mounted wireless transceiver maybe integrated with a device having voice recognition and/or facialrecognition. For example, the device may be a smart television. Theidentifier and location of the entity obtained by component 977 may beused to monitor and track progress and completion of events by theentity, as discussed in further detail below.

Platform 905 may track and record an event, including documentation ofownership assignment and resolution of the event. Natural languageunderstanding modules 930 may analyze and interpret information providedby the user via user and reporting interface 975 and/or conversationalcomputing interface 980. Review API 935 may analyze an event anddetermine whether any follow-up and/or resolution is needed.Learning/knowledgebase API 940 may obtain and analyze information aboutan event, such as a manual for a piece of equipment that describes howto use the piece of equipment (e.g., a protocol for operating the pieceof equipment). Rules API 945 may generate an event that includes aplurality of actions based on a rule or a plurality of rules, such asfederal, state, industry, and/or organization requirements.

Object data store 985 may include objects that are referenced by theAPIs and/or modules within platform 905. SQL data store may includestructured data in which there are relations between different entitiesand/or variables of the data. Rules data store 995 may includecompliance rules for a facility. Each of the compliance rules mayindicate the criteria for the rule, a chapter of the rule set where therule can be found, a level or levels of the facility to which the ruleis applied, a type of infraction that is caused by non-compliance withthe rule, and/or a status of the rule that indicates whether the rule isactive for the facility.

Platform 905 may evaluate the completion or the non-completion of anevent. For example, information from temporal data store 960 mayindicate whether an entity was scheduled to be present during the event,and information from access point data store 965 may indicate whetherthe entity accessed the facility through a controlled access pointbefore the event. Processing engine 950 may aggregate this informationto determine the likelihood that the entity completed the event.

Platform 905 may also predict the non-completion of an event. Forexample, processing engine 950 may use machine learning to predict thata minimum number of entities are required at a temporal point.Processing engine 950 may also receive information about functions ofentities at the facility from identifier API 910, and information aboutchronologies of entities at the facility from temporal API 915.Processing engine 950 may then determine whether the minimum number ofentities will be present at the temporal point. Processing engine 950may also determine whether entities with the required functions will bepresent at the temporal point. If either determination is negative,platform 905 may send a notification message indicating the potentialnon-completion of the event to user and reporting interface 975 and/orconversational computing interface 980.

Further, platform 905 may detect the non-completion of an event. Forexample, processing engine 950 may receive information about functionsof entities at the facility from identifier API 910, information aboutcontrolled access point entries of entities at the facility from entryAPI 920, and information about uncontrolled access point entries otherentities from arrival data API 925. Processing engine 950 may use thisinformation to determine whether the minimum number of entities arepresent. Processing engine 950 may also use this information todetermine whether entities with the required functions are present. Ifeither determination is negative, platform 905 may send a notificationmessage indicating the non-completion of the event to user and reportinginterface 975 and/or conversational computing interface 980.

Platform 905 may generate event vectors in order to determine whether anevent has been completed. Each event vector may be a data structure thathas a plurality of nodes that are spaced in time. Each node maycorrespond to an action. Processing engine 950 may generate eventvectors by incorporating information from various sources. For example,component 977 may provide a series of locations of an entity over time,and review API 935 may use this information to determine a series ofactions performed by the entity over time. Alternatively or in addition,user and reporting interface 975 and/or conversational computinginterface 980 may provide a series of actions of an entity over time.The event vector may be constructed by arranging the series of actionsas a plurality of nodes that are spaced in time.

FIG. 10 illustrates event vectors 1000, 1010, 1020, 1030, and 1040,according to several embodiments of the present disclosure. Eventvectors 1000, 1010, 1020, 1030, and 1040 are data structures having oneor more nodes that are spaced in time. Event vector 1000 includes nodes1001, 1002, 1003, and 1004; event vector 1010 includes nodes 1011 and1012; event vector 1020 includes nodes 1021, 1022, 1023, 1024, 1025, and1026; event vector 1030 includes nodes 1031, 1032, 1033, and 1034; andevent vector 1040 includes nodes 1041, 1042, 1043, and 1044.

Event vector 1040 may correspond to a protocol. For example, nodes 1041,1042, 1043, and 1044 of event vector 1040 may correspond to a temporalseries of required actions within a protocol. Rules API 945 may generateevent vector 1040 based on rules received from rules data store 995.

Event vectors 1000, 1010, 1020, and 1030 may correspond to events thatare tracked by processing engine 950. Review API 935 may determinewhether an event defined by event vector 1040 has been completed bymachine matching event vectors 1000, 1010, 1020, and/or 1030 to eventvector 1040. In this example, each of nodes 1031, 1032, 1033, and 1034of event vector 1030 matches respective nodes 1041, 1042, 1043, and 1044of event vector 1040. Accordingly, it is determined that the eventdefined by event vector 1040 was completed by event vector 1030. On theother hand, because event vectors 1000, 1010, and 1020 each have atleast one node that does not match respective nodes 1041, 1042, 1043,and 1044 of event vector 1040, it is determined that the event definedby event vector 1040 was not completed by event vectors 1000, 1010, and1020. Review API 935 may generate an output including a variable toindicate whether the event corresponding to event vector 1040 wascompleted.

FIGS. 11A-11C illustrate various diagrams of a facility 1100, accordingto several embodiments of the present disclosure. Facility 1100 may be astand-alone facility or may be part of a larger facility. Facility 1100may include a wide range of equipment. In some embodiments, facility1100 may include various rooms, corridors, entries, exits, desk areas,storage areas, and the like. For example, facility 1100 may include oneor more first rooms 1102, one or more second rooms 1104, one or morethird rooms 1106, a vestibule 1108, a supply room 1110, a server room1112, and a front desk 1124.

In some embodiments, arrival of an individual at facility 1100 maytrigger an event corresponding to a protocol. In some instances, theprotocol may include a set of actions to be completed by one or moreentities. The particular protocol, along with other protocols, may bestored in a local server 1114 located in server room 1112 or in a remoteserver outside facility 1100.

In many circumstances it may be beneficial to monitor and track progressand completion of events using a plurality of mobile wirelesstransceivers 1118 and mounted wireless transceivers 1120. Mobilewireless transceivers 1118 may be attached and/or carried by entities1116 and may include and/or be integrated with any type of electronicdevice (e.g., computer, mobile device, smart phone, laptop, electronicbadge, RFID tag, tablet, or pager). Mobile wireless transceivers 1118need not have both transmitting and receiving capabilities, but mayinstead have only transmitting capabilities (e.g., wireless transmitter)or only receiving capabilities (e.g., wireless receiver). For example,mobile wireless transceivers 1118 may comprise wireless transmitters,such as active RFID tags, capable of transmitting wirelesselectromagnetic signals.

In contrast, mounted wireless transceivers 1120 may be attached and/ormounted to a secured surface such as a ceiling, floor, wall, desk, etc.Mounted wireless transceivers 1120 need not have both transmitting andreceiving capabilities, but may instead have only transmittingcapabilities (e.g., wireless transmitter) or only receiving capabilities(e.g., wireless receiver). For example, mounted wireless transceivers1120 may comprise wireless receivers, such as active RFID readers,capable of receiving wireless electromagnetic signals. Mounted wirelesstransceivers 1120 may include and/or be integrated with any type ofelectronic device, such as a smart television having voice and/or facialrecognition. Mounted wireless transceivers 1120 may be configured toreceive and/or send wireless signals to mobile wireless transceivers1118, and mobile wireless transceivers 1118 may be configured to receiveand/or send wireless signals to mounted wireless transceivers 1120.

In one example, as entity 1116(1) carries mobile wireless transceiver1118(1) and moves near mounted wireless transceiver 1120(1), mountedwireless transceiver 1120(1) may transmit an identifier and locationrequest signal which is received by mobile wireless transceiver 1118(1).In response to receiving the identify and location request signal,mobile wireless transceiver 1118(1) may transmit a response wirelesssignal carrying information corresponding to entity 1116(1) to mountedwireless transceiver 1120(1) as well as to other nearby mounted wirelesstransceivers 1120, such as mounted wireless transceivers 1120(2) and1120(3). The response wireless signal may be received by one or more ofmounted wireless transceivers 1120(1), 1120(2), and 1120(3) and may beprocessed to extract identification data and location data correspondingto entity 1116(1). In another example, mounted wireless transceiver1120(1) may receive a signal carrying information corresponding toentity 1116(1) that is obtained by voice and/or facial recognition. Thesignal may be processed to extract identification data corresponding toentity 1116(1).

The response wireless signal may be processed by processors withinmounted wireless transceivers 1120(1), 1120(2), and 1120(3), or may beprocessed by local server 1114 which may be coupled with each of mountedwireless transceivers 1120(1), 1120(2), and 1120(3). For example, localserver 1114 may include one or more processors configured to detect,based on the response wireless signal, identification data and locationdata corresponding to entity 1116(1). In some embodiments, local server1114 may determine an identifier of entity 1116(1) based on theidentification data, and may determine a location of entity 1116(1)based on the location data. In some instances, the location may comprisean (X, Y) coordinate of where entity 1116(1) is situated within facility1100. The location may be determined based on a trilateration techniquewhere the signal level measured by each of mounted wireless transceivers1120(1), 1120(2), and 1120(3) are compared to each other and thelocation is calculated based on the comparison.

In some embodiments, the positioning of mounted wireless transceivers1120 within facility 1100 may improve the ability to identify and locateentities 1116. In reference to FIG. 11B, mounted wireless transceivers1120 may be positioned at various points of interest, such as rooms andareas in which actions within events take place or are likely to takeplace. For example, mounted wireless transceivers 1120 may be positionedwithin rooms (e.g., first rooms 1102, second rooms 1104, and third rooms1106) at a center point, at an entry point, or near a location in whichan individual is likely to be situated (e.g., near a chair or bed).Mounted wireless transceivers 1120 may also be positioned near otherpoints of interest where certain actions within events take place. Inone example, a protocol may include an action to be performed at astation near room 1104(1). The action may only be determined as beingperformed when the identifier and the location of entity 1116(1) areconfirmed to be within a threshold distance of one of stations 1122.

In reference to FIG. 11C, mounted wireless transceivers 1120 may bepositioned in a grid-like arrangement such that each is spacedequidistant from its nearest neighbors. Such an arrangement may have theadvantage of providing reliable and/or constant tracking of entities1116 within facility 1100. For example, mounted wireless transceivers1120 may be positioned such that “dead zones” do not exist withinfacility 1100 where mobile wireless transceiver 1118(1) is unable toreceive or send wireless signals to any of mounted wireless transceivers1120. In some embodiments, the periodicity of the spacing may differ inone direction from the other direction (e.g., spacing in the X-directionmay be greater or less than spacing in the Y-direction).

FIG. 12 illustrates a system 1200 comprising a plurality of localservers 1114, according to several embodiments of the presentdisclosure. Each local server 1114 is configured to communicate with aplurality of mobile wireless transceivers 1118 and/or a plurality ofmounted wireless transceivers 1120 at different facilities 1100. Localservers 1114 are configured to communicate with a processing engine 1250such that processing engine 1250 receives information corresponding tomultiple facilities 1100, perhaps dispersed over a wide geographic area.Processing engine 1250 may include various engines and generators,including a tracking engine 1252, a compliance engine 1254, a correctionengine 1256, and a documentation generator 1258.

FIG. 13 illustrates a processing engine 1250, according to severalembodiments of the present disclosure. Processing engine 1250 may be anexample of processing engine 950 discussed above. In some embodiments,tracking engine 1252 processes the wireless signals transmitted andreceived by mobile wireless transceivers 1118 and mounted wirelesstransceivers 1120. In some embodiments, tracking engine 1252 includes anidentification engine 1266 for detecting, based on the wireless signals,identification data corresponding to an entity. Identification engine1266 may then analyze the identification data to determine an identifierof the entity. In some embodiments, tracking engine 1252 includes alocalization engine 1268 for detecting, based on the wireless signals,location data corresponding to the entity. Localization engine 1268 maythen analyze the location data to determine one or more locations of theentity.

In some embodiments, the identifier and the location is sent by trackingengine 1252 to compliance engine 1254. Compliance engine 1254 mayretrieve a protocol from a protocol database 1264 to determine whethereach action of a set of actions defined by the protocol have beenperformed or are being performed. For each action of the set of actions,compliance engine 1254 may determine that an action was performed basedon the received identifier and location. Alternatively or additionally,compliance engine 1254 may determine that an action was performed basedon input received via an input interface 1260 indicating actionperformance. In some embodiments, upon determining that each action ofthe set of actions defined by a protocol have been performed, complianceengine 1254 may generate an output indicating that an eventcorresponding to the protocol was completed. The output may be stored ina message associated with a record.

In some embodiments, compliance engine 1254 may determine that one ormore actions of a protocol were not performed. Upon determining that oneor more actions of a protocol were not performed, compliance engine 1254may send a message to correction engine 1256 indicating that an eventcorresponding to the protocol was incomplete. Correction engine 1256 mayinclude a corrective step generator 1272 for generating corrective stepsfor the event. In some embodiments, corrective step generator 1272 maygenerate a protocol modification for modifying one or more protocolswithin protocol database 1264. Correction engine 1256 may also includean ownership assignor 1274 for assigning ownership of the correctivesteps to an owner. Ownership assignor 1274 may also send a notificationto the owner indicating the ownership and the corrective steps. In someembodiments, correction engine 1256 may include a follow up engine 1276for following up with the owner to determine whether or not thecorrective steps were performed by the owner. In some embodiments,correction engine 1256 may receive a user input via input interface 1260indicating that an event was incomplete. The user input may alsoindicate a protocol modification for modifying one or more protocolswithin protocol database 1264.

In some embodiments, documentation generator 1258 retrieves a protocolfrom protocol database 1264 and identifies one or more rules from rulesdatabase 1262 specifying a required documentation corresponding to atleast one of the set of actions defined by the protocol. In someinstances, documentation generator 1258 may cause tracking engine 1252to generate and/or retrieve an identifier and a location of an entity asdescribed herein. Documentation generator 1258 may generate the requireddocumentation based on the identifier and the location of the entity.

In some embodiments, documentation generator 1258 includes a presencetime processor 1270 for modifying an presence time recorded by anentity. In some instances, documentation generator 1258 receives a userinput via user interface 1260 corresponding to a recorded presence time.Documentation generator 1258 may cause tracking engine 1252 to generateand/or retrieve an identifier and a location of the entity as describedherein. After receiving the identifier and the location of the entity,presence time processor 1270 may generate a temporal dwell based on thelocation and/or location data. Presence time processor 1270 may thenrecalculate the recorded presence time as a function of the temporaldwell.

FIG. 14 illustrates various protocols stored within a protocol database1264, according to several embodiments of the present disclosure.Protocols may be requested and/or retrieved by compliance engine 1254and documentation generator 1258. In some instances, one or moreprotocols may be modified by corrective step generator 1272. In oneexample, a protocol (e.g., Protocol 1) includes seven actions indicatedby column 1402. An entity or multiple entities associated with eachaction is indicated by column 1404. Entities 1410 and 1412 may be firsttype of entity, while Entities 1414 and 1416 may be a second type ofentity. Whether a particular action is determined to be performed byusing data generated by tracking engine 1252 (e.g., Trackable) and/or byuser input received via input interface 1260 (e.g., Input) is indicatedby column 1406. In some instances, certain actions are only able to bedetermined to be performed by user input due to difficulties in trackingperformance using mobile wireless transceivers 1118 and mounted wirelesstransceivers 1120 (e.g., Room clean up). Protocols may be used togenerate event vectors as discussed above with reference to FIG. 12.

FIGS. 15A-15D illustrate various embodiments of presence time processor1270 which may, in some instances, be configured to modify an presencetime that is recorded by an entity to reflect a more accurate presencetime. In reference to FIG. 15A, presence time processor 1270 may receiveas inputs a recorded presence time 1502 and a temporal dwell 1504.Recorded presence time 1502 may be a single quantity or may a set ofstart and stop times from which a single quantity may be derived. Asshown in FIG. 15A, recorded presence time 1502 may not perfectlycorrespond to temporal dwell 1504 generated by tracking engine 1252. Forexample, a comparison of recorded presence time 1502 with temporal dwell1504 may yield an error signal 1506 comprised of one or moreover-reported times 1508 and one or more under-reported times 1510. Insome instances, over-reported times 1508 may correspond to times inwhich recorded presence time 1502 is represented but temporal dwell 1504is not represented. In contrast, under-reported times 1510 maycorrespond to times in which recorded presence time 1502 is notrepresented but temporal dwell 1504 is represented.

In some instances, error signal 1506 is passed through a filter 1512Aand then combined with recorded presence time 1502 to yield a modifiedpresence time 1514A. In some embodiments, filter 1512A may be configuredto set over-reported times 1508 to a negative value and under-reportedtimes 1510 to a positive value, having the effect of removingover-reported times 1508 from recorded presence time 1502 and addingunder-reported time 1510 to recorded presence time 1502. Althoughconfiguring filter 1512A in this manner may be effective at improvingaccuracy in many instances, there may be circumstances in which underand over reporting may be treated differently. This may be accomplishedby adjusting filter 1512A according to the following scenarios. Inreference to FIG. 15B, filter 1512B may be configured to setover-reported times 1508 to a negative value and under-reported times1510 to a value of zero, having the effect of removing over-reportedtimes 1508 from recorded presence time 1502 and ignoring under-reportedtime 1510. This results in a modified presence time 1514B. In referenceto FIG. 15C, filter 1512C may be configured to set over-reported times1508 to a value of zero and under-reported times 1510 to a positivevalue, having the effect of keeping over-reported times 1508 in recordedpresence time 1502 and adding under-reported time 1510 to recordedpresence time 1502. This results in a modified presence time 1514C. Inreference to FIG. 15D, filter 1512D may be configured to setover-reported times 1508 to a negative half value and under-reportedtimes 1510 to a positive half value, having the effect of keeping onlyhalf of over-reported times 1508 in recorded presence time 1502 andadding only half of under-reported time 1510 to recorded presence time1502. This results in a modified presence time 1514D. Otherpossibilities are contemplated.

FIGS. 16, 17, 18, and 19 illustrate example flow diagrams showingprocesses 1600, 1700, 1800, and 1900, according to at least a fewexamples. These processes, and any other processes described herein, areillustrated as logical flow diagrams, each operation of which representsa sequence of operations that can be implemented in hardware, computerinstructions, or a combination thereof. In the context of computerinstructions, the operations may represent computer-executableinstructions stored on one or more non-transitory computer-readablestorage media that, when executed by one or more processors, perform therecited operations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures and the likethat perform particular functions or implement particular data types.The order in which the operations are described is not intended to beconstrued as a limitation, and any number of the described operationscan be combined in any order and/or in parallel to implement theprocesses.

Additionally, some, any, or all of the processes described herein may beperformed under the control of one or more computer systems configuredwith specific executable instructions and may be implemented as code(e.g., executable instructions, one or more computer programs, or one ormore applications) executing collectively on one or more processors, byhardware, or combinations thereof. As noted above, the code may bestored on a non-transitory computer-readable storage medium, forexample, in the form of a computer program including a plurality ofinstructions executable by one or more processors. The computer-readablestorage medium is non-transitory.

FIG. 16 illustrates a process 1600 for determining whether an event wascompleted, according to several embodiments of the present disclosure.At operation 1602, a first event vector including a plurality of firstnodes that are spaced in time is received. In some embodiments, thefirst nodes correspond to a set of actions within a protocol, and atleast one action of the set of actions is performable by an entity. Forexample, a particular action may include a particular entity performingthe particular action at a particular location within a facility, suchas a room within the facility. In some embodiments, an action may not beassociated with a particular entity, such as an action requiring aparticular temperature in a room. Certain actions may be required priorto other actions.

At operation 1604, a wireless signal carrying information correspondingto the entity may be received. The wireless signal may be a signaltransmitted by a mobile wireless transmitter carried or attached to theentity and received by a mounted wireless receiver, or may be a signaltransmitted by a mounted wireless transmitter and received by a mobilewireless receiver. In one example, after a protocol is received, it maybe determined that the protocol includes an action to be performed by aspecific entity at a specific location within the facility. One or moremounted wireless transceivers in the vicinity of the specific locationmay then transmit a wireless signal which is received by a mobilewireless transceiver being carried by the specific entity that iscurrently performing the action. The mobile wireless transceiver maythen transmit a response wireless signal back to the one or more mountedwireless transceivers including information corresponding to thespecific entity. For example, the information may include identificationdata (e.g., the specific entity's identification number) and/or locationdata (e.g., a GPS location, or signal-strength data).

At operation 1606, identification data and location data correspondingto the entity may be detected based on the wireless signal. Detectingthe identification data and location data may include receiving thewireless signal and extracting the information contained within thewireless signal using any one of various data communication techniques(e.g., Quadrature amplitude demodulation). In some instances, detectingmay occur at a mobile wireless receiver and/or a mounted wirelessreceiver. In some instances, detecting may occur within a local orremote server where the information contained within the wireless signalis analyzed. In some embodiments, the location data may not only includea location but time information associated with the location. Forexample, the location data may be analyzed to determine that an entitywas in a particular location for a particular amount of time. Thelocation data may be provided for a plurality of time points.

At operation 1608, an identifier of the entity may be determined basedon the identification data. In some instances, information containedwithin the wireless signal includes the entity's identifier, such as anRFID tag number. In some embodiments, the identifier of the entity isdetermined based on the signal strength or the carrier frequency of thereceived signal (e.g., a first type of entity may have a high signalstrength while a second type of entity may have a low signal strength,etc.). In some embodiments, one or more entities may have the sameidentifier. For example, in some embodiments each of the first type ofentity may be associated with different ID numbers while each of thesecond type of entity may be associated with the same ID number.

At operation 1610, a location of the entity may be determined based onthe location data. In some embodiments, information contained within thewireless signal may include an (X, Y) coordinate of the entity'slocation. For example, in some embodiments a mobile wireless transceivermay be equipped with GPS capabilities such that the mobile wirelesstransceiver may directly report its position using a GPS coordinate. Insome embodiments, the location of the entity may be determined based ona trilateration technique where the signal level measured by differentmounted wireless transceivers is compared. For example, the location ofan entity may be determined to be in a particular room because wirelesssignals received by mounted wireless receivers equidistantly spacedsurrounding the particular room have similar received signal strengths.In some embodiments, mounted wireless receivers are positioned indifferent rooms, and the location of the entity is determined to be inthe room in which the received signal strength is the greatest.

At operation 1612, user input corresponding to the entity may bereceived. The user input may include a plurality of conditionals for theentity. The plurality of conditionals may indicate whether the entityperformed actions required by a protocol, along with the time andlocation at which the entity performed each of the actions. In someembodiments, the user input may be generated by a user using anapplication on a smart phone or other electronic device, which may ormay not be integrated with the mobile wireless transceiver being carriedby the entity or user. In some embodiments, the application may providean interface through which the entity or user may press a button, checka box, or type in information indicating that a particular action wasperformed. In some embodiments, certain actions within a protocol thatare not associated with an entity must be reported as being performedvia user input on an electronic device.

At operation 1614, a second event vector including a plurality of secondnodes that are spaced in time is generated. The second event vector maybe generated based on the information within the wireless signalcorresponding to the entity and/or the user input corresponding to theentity. For example, a node may be generated when it is determined thatan action was completed based on an identifier and a location of theentity that are obtained via operations 1604 and/or 1612. In someinstances, certain actions within a protocol that are deemed to be ofutmost importance may require both user input reporting that the actionwas performed and a determination based on the information derived fromthe wireless signal.

At operation 1616, the first event vector may be machine matched to thesecond event vector to generate a variable indicating whether an eventcorresponding to the first event vector is complete. If each of theplurality of the first nodes of the first event vector matches acorresponding one of the plurality of the second nodes of the secondevent vector, the variable indicates that the event corresponding to thefirst event vector is complete. On the other hand, if at least one ofthe plurality of the first nodes of the first event vector is mismatchedwith a corresponding one of the plurality of the second nodes of thesecond event vector, the variable indicates that the event correspondingto the first event vector is incomplete. For example, with regard to anaction corresponding to one of the plurality of the second nodes of thesecond event vector, a particular entity may arrive at the wrong room,may not spend an adequate amount of time in a room, or may perform theaction in an inadequate manner.

At operation 1618, an output including the variable indicating whetherthe event corresponding to the first event vector is complete isgenerated. In some embodiments, the output signal may cause the protocolcorresponding to the event to be deleted, reset, returned back to aremote server, or to be stored in a record (e.g., using a message). Insome embodiments, the output signal itself may be stored in a messageassociated with a record.

FIG. 17 illustrates a process 1700 for resolving an incomplete event,according to several embodiments of the present disclosure. At operation1702, it may be determined that an event was incomplete based on themachine matching of operation 1618.

At operation 1704, corrective steps for resolving the incomplete eventare generated. In some embodiments, the corrective steps may begenerated using a machine learning algorithm which analyzes defaultcorrective steps, corrective steps used in the past, and/or correctivesteps suggested via user input. In other embodiments, the correctivesteps may be suggested by a use. The corrective steps may includerepeating an unperformed action, repeating a protocol, and/or modifyinga protocol. The corrective steps may be generated such that they may beperformed similar to that of protocols, e.g., actions performable byentities.

At operation 1706, ownership of the corrective steps is assigned to anowner. The owner may be an entity who is to perform some or all of thecorrective steps, or may be a manager or department head associated withan entity who is to perform some or all of the corrective steps.Ownership may be assigned to a single or multiple owners, and may beassigned to an entity or organization. For example, failure to retrievewaste receptacles may cause ownership of the corrective steps to beassigned to a waste management company.

At operation 1708, a notification is sent to the owner indicating theownership and the corrective steps. The notification may be sent to theelectronic device of the owner, which may or may not be integrated witha mobile wireless transceiver. The notification may include a summarymessage indicating what event was incomplete, what corrective steps weregenerated, who was assigned ownership, and when the corrective steps areto be performed (i.e., deadline). In some instances, the notificationmay require that the owner reply to acknowledge receipt of thenotification.

At operation 1710, it is determined that the corrective steps wereperformed after a predetermined amount of time. In some instances, thedeadline established by the notification is used as a triggeringmechanism for determining whether the corrective steps were performed.Once triggered, a follow up engine may determine whether each step ofthe corrective steps were performed. Failure to perform a single stepmay cause a second notification to be sent to the owner indicatingeither the previous corrective steps or a new set of corrective steps(e.g., omitting the portion of the previous corrective steps that wereperformed).

FIG. 18 illustrates a process 1800 for generating documentation,according to several embodiments of the present disclosure. At operation1802, a protocol comprising a set of actions is identified. The protocolmay be similar to protocols described herein, and may include one ormore actions performable by an entity.

At operation 1804, one or more rules specifying a required documentationcorresponding to at least one of the set of actions is identified. Insome instances, each of the set of actions may be analyzed to determinewhether documentation is required. The corresponding rules may beidentified and analyzed so that the required documentation may begenerated. In some instances, the rules may specify the format of therequired documentation, and/or may specify a form with modifiable fieldsto be used. In some instances, the rules are stored in a local or remotedatabase (e.g., rules database 1262).

At operation 1806, a wireless signal carrying information correspondingto an entity is caused to be received based on the requireddocumentation. In some embodiments, if the required documentationincludes a modifiable field for the total amount of time an entity wasin a room, the wireless signal caused to be received may correspond tothe entity indicated in the required documentation. In some instances,operation 1806 may include the details described in reference tooperation 1604.

At operation 1808, identification data and location data correspondingto the entity are detected based on the wireless signal. In someinstances, operation 1808 may include the details described in referenceto operation 1606.

At operation 1810, an identifier of the entity is determined based onthe identification data. In some instances, operation 1810 may includethe details described in reference to operation 1608.

At operation 1812, a location of the entity is determined based on thelocation data. In some instances, operation 1812 may include the detailsdescribed in reference to operation 1610.

At operation 1814, the required documentation is generated based on theentity's identifier and the location. In some instances, the requireddocumentation is a list of time stamps corresponding to when an entityentered or exited a room. In some embodiments, the requireddocumentation is a pair of time stamps corresponding to when an entityentered and exited a facility, demonstrating that the entity did notwork longer than allowed by a state or federal law. In some embodiments,the required documentation is a list of entities that entered a roomduring a temporal window, demonstrating that the minimum required numberof entities were present during the temporal window. Other possibilitiesare contemplated using the techniques described herein.

FIG. 19 illustrates a process 1900 for modifying recorded presence time,according to several embodiments of the present disclosure. At operation1902, a recorded presence time is received from an entity. In someembodiments, the recorded presence time may be generated by a user usingan application on a smart phone or other electronic device, which may ormay not be integrated with the mobile wireless transceiver being carriedby the entity or user. In some embodiments, the application may providean interface through which the entity may enter information indicatingthe recorded presence time.

At operation 1904, a wireless signal corresponding to the entity iscaused to be received based on the recorded presence time. For example,if the entity entered a recorded presence time indicating that it was ina particular room for 45 minutes, the wireless signal caused to bereceived may involve one or both of the mobile wireless transceivercarried by the entity and the mounted wireless transceiver positioned inor near the particular room. In some instances, operation 1904 mayinclude the details described in reference to operation 1604.

At operation 1906, identification data and location data are detectedbased on the wireless signal. In some instances, operation 1906 mayinclude the details described in reference to operation 1606.

At operation 1908, an identifier of the entity is determined based onthe identification data. In some instances, operation 1908 may includethe details described in reference to operation 1608.

At operation 1910, a location of the entity is determined based on thelocation data. In some instances, operation 1910 may include the detailsdescribed in reference to operation 1610.

At operation 1912, a temporal dwell is generated based on the locationdata. In some embodiments, the location data may be associated withdifferent time stamps or time markers. For example, if it is determinedthat an entity is in a particular room based on the received wirelesssignal, the time at which the wireless signal was received may be usedto generate the temporal dwell. For instance, the temporal dwell may becalculated as the difference between a first time at which a firstwireless signal was received and a second time at which a secondwireless signal was received.

At operation 1914, the recorded presence time and the temporal dwell areprocessed to modify the recorded presence time. As described inreference to FIGS. 15A-15D, various approaches may be employed to modifythe recorded presence time. In a first approach (described in referenceto FIG. 15A), the temporal dwell is used to modify the recorded presencetime by removing over-reported times and adding under-reported times. Ina second approach (described in reference to FIG. 15B), the temporaldwell is used to modify the recorded presence time by removing bothover-reported times and under-reported times. In a third approach(described in reference to FIG. 15C), the temporal dwell is used tomodify the recorded presence time by adding both over-reported times andunder-reported times. In a fourth approach (described in reference toFIG. 15D), the temporal dwell is used to modify the recorded presencetime by adding only half of over-reported times and under-reportedtimes.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments may be practiced without these specific details.For example, circuits may be shown in block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquesmay be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove may be done in various ways. For example, these techniques,blocks, steps and means may be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitsmay be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flowchart, a flow diagram, a swim diagram, a dataflow diagram, a structure diagram, or a block diagram. Although adepiction may describe the operations as a sequential process, many ofthe operations can be performed in parallel or concurrently. Inaddition, the order of the operations may be re-arranged. A process isterminated when its operations are completed, but could have additionalsteps not included in the figure. A process may correspond to a method,a function, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination corresponds to a return ofthe function to the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks may bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment may becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. may be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, token passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory. Memory may be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may representone or more memories for storing data, including read only memory (ROM),random access memory (RAM), magnetic RAM, core memory, magnetic diskstorage mediums, optical storage mediums, flash memory devices and/orother machine readable mediums for storing information. The term“machine-readable medium” includes, but is not limited to portable orfixed storage devices, optical storage devices, and/or various otherstorage mediums capable of storing that contain or carry instruction(s)and/or data.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed is:
 1. A computer-implemented method for assessingcompletion of events, the computer-implemented method comprising:receiving a first event vector, wherein the first event vector comprisesa plurality of first nodes that are spaced in time, and the plurality ofthe first nodes corresponds to a temporal sequence of actions within aprotocol; at least one of: receiving a wireless signal carryinginformation corresponding to an entity, wherein the informationcomprises a location of the entity as a function of time and anidentifier of the entity; or receiving input corresponding to theentity, wherein the input comprises a plurality of conditionals for theentity; generating a second event vector, wherein the second eventvector comprises a plurality of second nodes that are spaced in time,and wherein the second event vector is generated as a function of atleast one of the information corresponding to the entity or the inputcorresponding to the entity; machine matching the first event vector tothe second event vector, wherein the machine matching generates avariable indicating whether an event corresponding to the first eventvector is complete; and generating an output comprising the variable,wherein: if each of the plurality of the first nodes of the first eventvector matches a corresponding one of the plurality of the second nodesof the second event vector, the variable indicates that the eventcorresponding to the first event vector is complete, and if at least oneof the plurality of the first nodes of the first event vector ismismatched with the corresponding one of the plurality of the secondnodes of the second event vector, the variable indicates that the eventcorresponding to the first event vector is incomplete.
 2. Thecomputer-implemented method of claim 1, wherein the wireless signal istransmitted by a mobile wireless transmitter and received by a mountedwireless receiver, and wherein the mobile wireless transmitter iscarried by the entity.
 3. The computer-implemented method of claim 1,wherein the wireless signal is transmitted by a mounted wirelesstransmitter and received by a mobile wireless receiver, and wherein themobile wireless receiver is carried by the entity.
 4. Thecomputer-implemented method of claim 1, further comprising: storing theoutput in a message associated with a record.
 5. Thecomputer-implemented method of claim 2, wherein the mobile wirelesstransmitter is integrated with a computer, a mobile device, a smartphone, a laptop, an electronic badge, an RFID tag, a tablet, or a pager.6. The computer-implemented method of claim 2, wherein the mountedwireless receiver is integrated with a device having at least one ofvoice recognition or facial recognition.
 7. The computer-implementedmethod of claim 1, further comprising: scanning, by a scanning device, abag machine-readable (MR) tag coupled to or integrated with a fluid bag,the bag MR tag encoded with a bag identifier such that the scanningdevice is configured to read the bag identifier upon scanning the bag MRtag; scanning, by the scanning device, a pump MR tag coupled to orintegrated with an infusion pump, the pump MR tag encoded with a pumpidentifier such that the scanning device is configured to read the pumpidentifier upon scanning the pump MR tag; transmitting, by the scanningdevice, the bag identifier and the pump identifier to a processingengine; receiving, by the processing engine, the bag identifier and thepump identifier from the scanning device; determining, by the processingengine, a bag volume associated with the fluid bag based on the bagidentifier; receiving, by the processing engine, pump data from theinfusion pump, wherein the pump data is indicative of one or more of aninfusion rate, an infusion time, a volume to be infused (VTBI), and thepump identifier; determining, by the processing engine, based on atleast the bag volume and the one or more of the infusion rate, theinfusion time, the VTBI, and the pump identifier, a depletion timeassociated with the fluid bag; and sending, by the processing engine, ata predetermined amount of time prior to the depletion time, an alertindicating imminent depletion of the fluid bag.
 8. A system comprising:one or more data processors; and a non-transitory computer readablestorage medium containing instructions that, when executed on the one ormore data processors, cause the one or more data processors to performactions including: receiving a first event vector, wherein the firstevent vector comprises a plurality of first nodes that are spaced intime, and the plurality of the first nodes corresponds to a temporalsequence of actions within a protocol; at least one of: receiving awireless signal carrying information corresponding to an entity, whereinthe information comprises a location of the entity as a function of timeand an identifier of the entity; or receiving input corresponding to theentity, wherein the input comprises a plurality of conditionals for theentity; generating a second event vector, wherein the second eventvector comprises a plurality of second nodes that are spaced in time,and wherein the second event vector is generated as a function of atleast one of the information corresponding to the entity or the inputcorresponding to the entity; machine matching the first event vector tothe second event vector, wherein the machine matching generates avariable indicating whether an event corresponding to the first eventvector is complete; and generating an output comprising the variable,wherein: if each of the plurality of the first nodes of the first eventvector matches a corresponding one of the plurality of the second nodesof the second event vector, the variable indicates that the eventcorresponding to the first event vector is complete, and if at least oneof the plurality of the first nodes of the first event vector ismismatched with the corresponding one of the plurality of the secondnodes of the second event vector, the variable indicates that the eventcorresponding to the first event vector is incomplete.
 9. The system ofclaim 8, wherein the wireless signal is transmitted by a mobile wirelesstransmitter and received by a mounted wireless receiver, and wherein themobile wireless transmitter is carried by the entity.
 10. The system ofclaim 8, wherein the wireless signal is transmitted by a mountedwireless transmitter and received by a mobile wireless receiver, andwherein the mobile wireless receiver is carried by the entity.
 11. Thesystem of claim 8, wherein the actions further include: storing theoutput in a message associated with a record.
 12. The system of claim 9,wherein the mobile wireless transmitter is integrated with a computer, amobile device, a smart phone, a laptop, an electronic badge, an RFIDtag, a tablet, or a pager.
 13. The system of claim 9, wherein themounted wireless receiver is integrated with a device having at leastone of voice recognition or facial recognition.
 14. The system of claim11, wherein the actions further include: obtaining the message; parsingdata within the message to identify one or more components of the data,the one or more components being arranged according to a first order,and wherein at least one of the one or more components comprises astring; identifying a component type of a plurality of component typesassociated with each of the one or more components of the data; aligningthe one or more components of the data based on the component type suchthat the one or more components are arranged according to a secondorder, the second order being different than the first order; adding atransaction operation property to the data, wherein the transactionoperation property determines at least one of a create operation, anupdate operation, a delete operation, or a cancel operation;transforming the string of the at least one of the one or morecomponents into a programming object; classifying each of the one ormore components as a resource of a plurality of resources; andoutputting the message toward a destination system or a data warehouse.15. A computer-program product tangibly embodied in a non-transitorymachine-readable storage medium, including instructions configured tocause one or more data processors to perform actions including:receiving a first event vector, wherein the first event vector comprisesa plurality of first nodes that are spaced in time, and the plurality ofthe first nodes corresponds to a temporal sequence of actions within aprotocol; at least one of: receiving a wireless signal carryinginformation corresponding to an entity, wherein the informationcomprises a location of the entity as a function of time and anidentifier of the entity; or receiving input corresponding to theentity, wherein the input comprises a plurality of conditionals for theentity; generating a second event vector, wherein the second eventvector comprises a plurality of second nodes that are spaced in time,and wherein the second event vector is generated as a function of atleast one of the information corresponding to the entity or the inputcorresponding to the entity; machine matching the first event vector tothe second event vector, wherein the machine matching generates avariable indicating whether an event corresponding to the first eventvector is complete; and generating an output comprising the variable,wherein: if each of the plurality of the first nodes of the first eventvector matches a corresponding one of the plurality of the second nodesof the second event vector, the variable indicates that the eventcorresponding to the first event vector is complete, and if at least oneof the plurality of the first nodes of the first event vector ismismatched with the corresponding one of the plurality of the secondnodes of the second event vector, the variable indicates that the eventcorresponding to the first event vector is incomplete.
 16. Thecomputer-program product of claim 15, wherein the wireless signal istransmitted by a mobile wireless transmitter and received by a mountedwireless receiver, and wherein the mobile wireless transmitter iscarried by the entity.
 17. The computer-program product of claim 15,wherein the wireless signal is transmitted by a mounted wirelesstransmitter and received by a mobile wireless receiver, and wherein themobile wireless receiver is carried by the entity.
 18. Thecomputer-program product of claim 15, wherein the actions furtherinclude: storing the output in a message associated with a record. 19.The computer-program product of claim 16, wherein the mobile wirelesstransmitter is integrated with a computer, a mobile device, a smartphone, a laptop, an electronic badge, an RFID tag, a tablet, or a pager.20. The computer-program product of claim 16, wherein the mountedwireless receiver is integrated with a device having at least one ofvoice recognition or facial recognition.